2016-01-18 - 24216 - Spec - Batch Wire Processing for M&T #FIOutgoingpayments #US #BankMaster

SPECIFICATIONS

24216-Spec- Batch Wire Processing

Purpose

The current manual wire process requires significant time commitment from treasury and is subject to keying errors. The project is to implement a batch wire process where payment data is communicated by FTP from SAP to M&T Bank, and thus wire payments can be created and cleared automatically.

Admin Info

Purpose	Batch Wire Processing
Requested By	Jingsha/Baiwa
Spec Created By	Raghav
Spec Created Date	06/24/2015
Spec QA by	Raghav
Objects	PAYMZWIRE_MNT ZWIRE_MNT Z_FI_WIRE_FILENAME Z_FI_WIRE_EXIT VC_TFPM042F VC_T042ZL V_T042E VC_T012 VC_BANKDET VC_TFPM042FC
Document Status	Resolved

Estimates

Sl.No	Activity	Estimation in Hours
1	Research	40
2	Documentation	12
3	Development/ Config	70
4	Unit test in DEV	60
5	Unit test in QUA	08
6	Other activity
	TOTAL	190

References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]
20200 : Batch wire processing

Documents

[Attach any document(s) received for the requirement(s)]

Spec Changes

[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.	Change Details	Requested By	Requested On	Notes if any
1.	Email Notification to Vendor when payment is made.	Baiwa	07/10/2015
2.	Email notification to Treasury team if the master data is changed.	Baiwa	07/10/2015	Requirement stopped by Jingsha
3.	Merging of DME File for different country company code.	Baiwa	07/15/2015	As it is not possible in standard SAP NEC will merge the file using 3rd party software
4.	Creation of DME file name	Jingsha	07/25/2015
5.	Bank Account number exceeded the SAP standard field length 18 Char	Baiwa	10/07/2015
6.	Input 4 digit intermediary bank number for 'RBK' foreign bank	Baiwa	11/03/2015
7.	Batch Wire Enhancement	Baiwa	01/18/2016	Received new ticket 24216 previous was 20200 - Requirement was stopped by NEC on 03/07/2016

Functional Requirement

Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]

The current manual wire process requires significant time commitment from treasury and is subject to keying errors. The project is to implement a batch wire process where payment data is communicated by FTP from SAP to M&T Bank, and thus wire payments can be created and cleared automatically.

Batch Wire Client Implementation ToolKit.pdf Batch Wire Design Document.docx

Batch Wire Enhancement

Business required us to send additional beneficiary information to the bank which can be store in the fields OB1 and OB2. This is required for certain countries such as Brazil.

In Scope:

[List the activities to be included in scope]

Out of Scope:

[Out of scope activities]

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]

Automatic Payment Process to vendor for batch wire payments is done through payment media workbench format ZWIRE_MNT with new payment method "Z". As per the bank specifications we have to create new DME flat file format ZWIRE_MNT.
For File naming convention : Wire_NewEra_<Company code>_<Timestamp start with YYYYMMDDHHMMSS>.TXT we have to create the new Functional Exit.
Exceeded bank account number we have to create new functional exit to merge the bank account and bank reference fields from the vendor master data.
For field 4 in RBK international payments we have to put the bank branch field from vendor master data.

Wire_NewEra_0010_20150910081356.TXT

7. Batch wire enhancement

We can add two new fields in the vendor master data address tab as below screen shots.
Enh 2.png

This fields can store the data in the LFA1 table and the total estimate for this enhancement, DME file setup and testing may take 60-70 hours.

Test Plan

[List test scenarios/cases to be executed here]

APP run for the DME output as per the bank format

Test ID	Test Scenario	Expected Results
FI-001	Create the APP F110 for the company code 0010	DME File should generate for the as per the Bank format.
FI-002	Create the APP F110 for the company code 0014	DME File should generate for the as per the Bank format.
FI-003	Create the APP F110 for the company code 0020	DME File should generate for the as per the Bank format.
FI-004	Create the APP F110 for the company code 0050	DME File should generate for the as per the Bank format.

APP run for the DME output with fixed length, Domestic and foreign banks.

Test ID	Test Scenario	Expected Results
FI-001	APP F110 run for Batch wire payments for CoCd 0010	DME file should display the field length as mentioned, fields should not merge with other, differentiate dometic and foreign bank
FI-002	APP F110 run for Batch wire payments for CoCd 0014	DME file should display the field length as mentioned, fields should not merge with other, differentiate dometic and foreign bank
FI-003	APP F110 run for Batch wire payments for CoCd 0020	DME file should display the field length as mentioned, fields should not merge with other, differentiate dometic and foreign bank
FI-004	APP F110 run for Batch wire payments for CoCd 0050	DME file should display the field length as mentioned, fields should not merge with other, differentiate dometic and foreign bank
FI-005	APP F110 run for Batch wire payments for CoCd 0055	DME file should display the field length as mentioned, fields should not merge with other, differentiate dometic and foreign bank

APP run for the DME output with bank account merged with bank reference field and foreign banks RBK field 4 with 4 digit intermediary bank ID.

Test ID	Test Scenario	Expected Results
FI-001	APP run for company code 0010 with multiple countries	1) DMEE file field 'CAC' bank account number should display default merged data with bank account number and bank reference fields and 'BN2' should display blank data. 2) In field 4 of 'RBK' 4 digit intermediary bank ID should display with bank branch field